ci: cap Vercel deploy jobs at 30min (prevent concurrency lockups)#710
Merged
Conversation
The main CI concurrency group is cancel-in-progress:false (don't kill a deploy mid-flight), so a hung job blocks all later runs/deploys. The four Vercel deploy jobs had no timeout (GitHub's 6h default) — today a hung 'Deploy → Vercel' froze deploys for ~4h. A 30min cap (legit deploys take ~12min) turns a hang into a fast failure instead of a multi-hour lockup. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
|
Claude finished @blove's task in 33s —— View job Review
The change is correct and well-targeted. Four lines added, each placing What I checked:
No issues found. This is a straightforward, well-scoped fix for a real incident. Good to merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
timeout-minutes: 30to the four Vercel deploy jobs inci.yml(Deploy → Vercel,Canonical demo → Vercel,ag-ui demo → Vercel,Cockpit — deploy smoke dry-run), which previously had no timeout (GitHub's 6h default).Why
The main CI concurrency group is
cancel-in-progress: false(intentional — don't kill a deploy mid-flight), so a single hung job blocks all later runs and deploys in the group. Today aDeploy → Verceljob hung for ~4 hours and froze main deploys. A 30-min cap (legitimate deploys take ~12 min) turns a hang into a fast failure instead of a multi-hour lockup.Not touching the concurrency semantics or strengthening anything else — just bounding the failure mode.
Test Plan
🤖 Generated with Claude Code